What you actually own when you buy software

Three questions decide whether you are buying an asset or renting a dependency: who holds the repository, who holds the domain, and what happens on the day you stop paying.

The question nobody asks on the demo call

Software procurement conversations are about features. Can it do recurring appointments, does it text reminders, does it integrate with the accounting package. Those are reasonable questions and they are all downstream of one that rarely comes up: at the end of this, what do we have?

With a subscription the answer is access. You have the right to use something for as long as you keep paying. That is not automatically bad. It is only bad when nobody said it out loud, and the business planned as though it were buying a thing.

Question one: who holds the repository

If a system was built for you, someone has the source code. If that someone is the vendor, and the contract does not transfer it, you cannot hire another developer to continue the work. You can only hire the vendor.

Ask where the code lives and whose account it lives in. On our builds it sits in the client’s repository from the first commit, which sounds like a technicality until the day it matters.

Question two: who holds the domain and the accounts

A surprising number of businesses discover during a dispute that their domain is registered to an agency, their hosting is on an agency card, and their customer data is inside a platform account they cannot administer.

Each one of those is a lever. Held by someone else, they turn a commercial disagreement into an operational emergency. The fix is unglamorous: registrar in your name, infrastructure on your billing, admin access held by someone who works for you.

Question three: what happens if you stop paying

This is the only question that produces a genuinely useful answer, because it forces the vendor to describe the failure mode.

With most subscriptions the honest answer is that the software stops and you export what you can. With a system you own, hosting has to be paid and support ends, but the software keeps running and the data stays where it is. That difference is the whole distinction between an asset and a dependency.

Where subscriptions are still correct

If a tool does one job well and switching later would be easy, renting it is the right call. Nobody should commission a custom email client. The calculation changes when a tool holds the customer record, when three tools hold three versions of it, or when the per-seat line grows faster than the team.

The point is not that ownership always wins. It is that most businesses have never been told which one they are buying.